structure: 
headline
line number
original quote
possible problem

----------
----------
Simple Use Example; 
line 617: 
<p>You must find the programs and their projects as well as the JACK connections as they were when you closed the session, and everything therefore works without any further manipulation.

- Probably "You will find" is meant. 
----------
----------



----------
----------
Simple Use Example: 
line 618: 
One of the advantages of modularity in this specific case is that once you have finished taking the guitar, you can stop Guitarix so as not to overload the processor unnecessarily, and it will still be easy to restart it if necessary.</p>

- Not clear to me, i only can imagine "recording the guitar" is meant,
  but am not sure. 
----------
----------



----------
----------
Duplicate current session
line 647
This is the equivalent of the well-known "Save As &#8230;&#8203;", except that RaySession has to stop and restart most programs to switch between sessions. Avoid duplicating a session with a lot of audio files, it could take a long time, but fortunately such an operation can be undone.</p>

- it might be: "but fortunately such an operation can be "stopped", not
  "undone"
----------
----------



----------
----------
Rename the session
line 651
It will then be necessary to stop all the clients.<br>

- will they be stopped by using "rename" or will the user have to do it
  himself. If automatically i would go for: 
"All clients will be stopped during rename"
or such. "necessary" sounds like the user is in charge
----------
----------



----------
----------
Add excecutable Window
line 980
If you leave the <strong>NSM protocol</strong> checked, it will not be possible to add an executable to an absolute path, ... 

- i wouldn't say "add an executable to an absolute path", but rather
  "use the absolute path of an executable to add it" or "add executable
via path" or such, as you don't add it to the  excecutable to the path,
you call it like that (?)
----------
----------



----------
----------
Add a program not provided
line 1284
<p>Click <strong>Validate</strong> at the possible warning window.<br>

- To me the whole paragraph how to save a project in audacity is a bit unclear. It might ! be description and pictures are too close to
the Mate DE or are too specific. A more abstract and less detailed approach might be more clear (?). Like: 
"In Audacity go to Menu, File, Save Project, Save; save the Audacity Project in the Clients folder of Audacity in the Session folder of the RaySession running. Use the exact name of the Session for the Audacity project too. "

I am very unsure if the given version isn't perfectly fine, and it is just me. 
----------
----------



----------
----------
damon options
line 1384
<p>Here is the detail of the different options:</p>

----------
----------
- probably "here are the details the different options:



----------
----------
damon options
line 1353
<p>In audio production, it is often used to create an audio or midi file with one program and then load it into another.

- either: "in audio production it often is useful create an audio or midi file with one program and then load it into another"
but probably what is meant: "In audio production, creating audio or midi file with one program and load it into another is a usual case"
----------
----------


----------
----------
Remember optional GUI states
line 1383
<p>This option only concerns NSM clients capable of showing/hiding their graphical interface. Without this option, some of them will always start hidden, others will remember if they were visible when they were last saved. With this option enabled, the graphical interfaces will be displayed when the session is ready if they were visible during the last save or if the client has never been launched.</p>

- I don't understand what they do. Will they start the way they were closed/saved last time? Or will they always be visible?
As usual: might well be me. 
----------
----------



----------
----------
session scripts
line 1434

<code>~/Ray Sessions/avec_script_de_foo/ma session</code></p>

- The examples for the paths are in french. Not sure if relevant at all, but the french name gives some extra info an english reader might miss. Probably obvious enough the way it is. Just saying
----------
----------



----------
----------
Special cases
line 1603

<p>move the session to a sub-folder containing the good one <code>ray-scripts</code> folder</p>

I don't understand the alternative, second  method how to make old sessions sensible  for JACK configuration  at all. 
To me it is not clear what needs to get copied where. 
----------
----------



----------
----------
under the hood
line 1617

Tap <code>raysession --help</code> to see how.</p>

Probably "Type" is meant, not Tap. 
----------
----------

----------
----------
Control RaySession from the commandline
line 1634

<p>One might think that there is no point in using <code>ray_control</code> since the command <code>oscsend</code> allows to send an OSC message to the daemon, it is false.<br>

I'd say either: 
"If one might think that ...,  then it is false"
or 
"One might think that ..., but it is false.  
